Systems and methods for the synchronization of transaction data

ABSTRACT

A method comprising receiving a category of metadata from an accounting software system, receiving a plurality of metadata labels associated with the category of metadata from the accounting software, receiving a ROC, receiving an association of one of the plurality of the metadata labels with the ROC, and/or transmitting the ROC and the association of the one of the plurality of the metadata labels with the ROC to the accounting software system. The category of metadata may comprise a card member name, an image of a receipt associated with the ROC, a description, and the like.

FIELD

The present disclosure generally relates to the synchronization of transaction data between an accounting software system and a transaction account issuer system.

BACKGROUND

Typically, a customer using accounting software may utilize the software to update and enter metadata associated with a variety of transactions. This process may be cumbersome, in that the customer may only enter data periodically (as opposed to in response to a particular transaction) as well as for a large number of transactions. In addition, the customer often manually enters data in the accounting software based upon a transaction account statement. Thus, systems and methods that facilitate and enhance data entry and synchronization processes between accounting systems and transaction account systems are desirable.

SUMMARY

A method comprises receiving a category of metadata from an accounting software system, receiving a plurality of metadata labels associated with the category of metadata from the accounting software, receiving a ROC, receiving an association of one of the plurality of the metadata labels with the ROC, and/or transmitting the ROC and the association of the one of the plurality of the metadata labels with the ROC to the accounting software system. In various embodiments, the category of metadata may comprise a card member name, an image of a receipt associated with the ROC, a description, and the like. The method may further comprise receiving an image of a receipt associated with the ROC and associating the image with the ROC. The ROCs stored by the accounting software system may be synchronized with ROCs stored by the computer-based system in response to the transmitting. The method may further comprise notifying a customer in response to receiving the ROC. The notifying may occur in response to receiving the ROC and/or in real time and/or near real time.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present disclosure will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, wherein like numbers represent like components:

FIG. 1 illustrates, in accordance with various embodiments, a system for synchronizing transaction data between a transaction account issuer system and an accounting software system;

FIG. 2 illustrates, in accordance with various embodiments, a process for synchronizing transaction data between a transaction account issuer system and an accounting software system;

FIG. 3 illustrates, in accordance with various embodiments, a screenshot of an accounting software system, in which the system is configured to receive a selection of a transaction account to be synchronized;

FIG. 4 illustrates, in accordance with various embodiments, a screenshot of an accounting software system, in which the system is configured to receive a selection of a plurality of categories of metadata; and

FIG. 5 illustrates, in accordance with various embodiments, a screenshot of an accounting software system, in which the system lists a plurality of records of charge (“ROCs”), and in which the system permits a customer to associate a ROC with a category of metadata, as well as a metadata label within the category of metadata.

DETAILED DESCRIPTION

The detailed description of exemplary embodiments herein makes reference to the accompanying drawings, which show the exemplary embodiments by way of illustration and their best mode. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.

As used herein, a metadata label may comprise any label, indicator and/or description that a customer wishes to associate with a ROC (such as those depicted at FIG. 5). Further, as used herein, a metadata category may comprise any category of labels, indicators and/or descriptions that a customer wishes to associated with a ROC (such as those also depicted at FIG. 5).

As used herein, the phrase “real time” and/or “near real time” and the like may mean any period of time during which a ROC is received and/or associated with a metadata category and/or metadata label. For example, in various embodiments, any of these terms may mean a period of time immediately following and/or shortly following a transaction, an event, an occurrence, and the like. In various embodiments, the period of time may include a period of picoseconds, nanoseconds, microseconds, milliseconds, seconds, minutes, hours, days, and the like.

Phrases and terms similar to “financial institution,” “transaction account issuer” and “payment processor” may include any person, entity, software and/or hardware that offers transaction account services. Although often referred to as a “financial institution,” the financial institution may represent any type of bank, lender or other type of account issuing institution, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution.

The terms “payment vehicle,” “financial transaction instrument,” “transaction instrument,” or “transaction account product” may be used interchangeably throughout to refer to a financial instrument. As used herein, an account code may or may not be associated with a physical financial instrument.

Phrases and terms similar to a “buyer,” “participant”, “consumer,” and “user” may include any person, entity, software and/or hardware that receives items in exchange for consideration (e.g. financial payment). For example, a buyer may purchase, lease, rent, barter or otherwise obtain items from a supplier and pay the supplier using a transaction account.

Phrases or terms similar to a “processor” (such as a payment processor) or “transaction account issuer” may include a company (e.g., a third party) appointed (e.g., by a merchant) to handle transactions for merchant banks. Processors may be broken down into two types: front-end and back-end. Front-end processors have connections to various transaction accounts and supply authorization and settlement services to the merchant banks' merchants. Back-end processors accept settlements from front-end processors and, via The Federal Reserve Bank, move money from an issuing bank to the merchant bank. In an operation that will usually take a few seconds, the payment processor will both check the details received by forwarding the details to the respective account's issuing bank or card association for verification, and may carry out a series of anti-fraud measures against the transaction. Additional parameters, including the account's country of issue and its previous payment history, may be used to gauge the probability of the transaction being approved. In response to the payment processor receiving confirmation that the transaction account details have been verified, the information may be relayed back to the merchant, who will then complete the payment transaction. In response to the verification being denied, the payment processor relays the information to the merchant, who may then decline the transaction.

As used herein, “transmit” may include sending electronic data from one system component to another over a network connection. Additionally, as used herein, “data” may include encompassing information such as commands, queries, files, data for storage, and the like in digital or any other form.

Phrases or terms similar to “transaction account” may include any account that may be used to facilitate a financial transaction. A “transaction account” as used herein refers to an account associated with an open account or a closed account system (as described herein). The transaction account may exist in a physical or non-physical embodiment. For example, a transaction account may be distributed in non-physical embodiments such as an account number, frequent-flyer account, and telephone calling account or the like. Furthermore, a physical embodiment of a transaction account may be distributed as a financial instrument.

In general, transaction accounts may be used for transactions between the user and merchant via any suitable communication means, such as, for example, a telephone network, intranet, the global, public Internet, a point of interaction device (e.g., a point of sale (POS) device, personal digital assistant (PDA), mobile telephone, kiosk, etc.), online communications, off-line communications, wireless communications, and/or the like.

An “account”, “account code”, or “account number”, as used herein, may include any device, code, number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric or other identifier/indicia suitably configured to allow the consumer to access, interact with or communicate with the system (e.g., one or more of an authorization/access code, personal identification number (PIN), Internet code, other identification code, and/or the like). The account number may optionally be located on or associated with a rewards card, charge card, credit card, debit card, prepaid card, telephone card, embossed card, smart card, magnetic stripe card, bar code card, transponder, radio frequency card or an associated account. The system may include or interface with any of the foregoing cards or devices, QR codes, Bluetooth, Near Field Communication, or a transponder and RFID reader in RF communication with the transponder (which may include a fob). Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation.

Moreover, the system, computing unit or device discussed herein may include a “pervasive computing device,” which may include a traditionally non-computerized device that is embedded with a computing unit. Examples can include watches, Internet enabled kitchen appliances, restaurant tables embedded with RF readers, wallets or purses with imbedded transponders, etc.

The account code may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency, wireless, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A customer account code may be, for example, a sixteen-digit transaction account code, although each transaction account provider has its own numbering system, such as the fifteen-digit numbering system used by American Express. Each company's transaction account codes comply with that company's standardized format such that the company using a fifteen-digit format will generally use three-spaced sets of numbers, as represented by the number “0000 000000 00000”. The first five to seven digits are reserved for processing purposes and identify the issuing bank, card type, etc. In this example, the last (fifteenth) digit is used as a sum check for the fifteen digit number. The intermediary eight-to-eleven digits are used to uniquely identify the customer. A merchant account code may be, for example, any number or alpha-numeric characters that identify a particular merchant for purposes of card acceptance, account reconciliation, reporting, or the like.

It should be noted that the transfer of information in accordance with the present disclosure, may be completed in a format recognizable by a merchant system or account issuer. In that regard, by way of example, the information may be transmitted from a contactless (e.g., an RFID device) to a contactless (e.g., RFID) reader or from the contactless reader to the merchant system in a variety of formats, e.g., magnetic stripe or multi-track magnetic stripe format.

Referring to FIG. 1, a system 100 for synchronizing an accounting software system 102 with a transaction account issuer system 106 is disclosed. The system 100 may comprise, as shown, and a configured to synchronize with an accounting software system is shown. The system may comprise an accounting software system 102 a network 104, and a transaction account issuer system 106. Either or both of the accounting software system 102 and/or the transaction account issuer system 106 may comprise any suitable hardware and/or software. For example, in various embodiments, the accounting software system 102 may comprise a multi-tier computer architecture such as a client-server architecture comprising one or more computers, computer servers, and/or the like. The accounting software system 102 may, in various embodiments, comprise a web-client as described below.

A web-client may, accordingly, include any device (e.g., personal computing device/mobile communication device) which communicates via any network. A web-client may be associated with and/or used by a consumer, a merchant, or both. A web-client may comprise a variety of browsing software or browser applications (e.g., Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Apple Safari, or any other of the myriad software packages available for browsing the internet). Such browser applications may comprise Internet browsing software installed within a computing unit or a system to conduct online transactions and/or communications. These computing units or systems may take the form of a computer or processor, or a set of computers/processors, although other types of computing units or systems may be used, including laptops, notebooks, hand held computers, personal digital assistants, cellular phones, smart phones (e.g., iPhone®, BlackBerry®, Droid®, etc.) set-top boxes, workstations, computer-servers, main frame computers, mini-computers, PC servers, pervasive computers, network sets of computers, personal computers, such as iPads, iMACs, and MacBooks, kiosks, terminals, point of sale (POS) devices and/or terminals, televisions, or any other device capable of receiving data over a network 104.

As those skilled in the art will appreciate, a web-client may include an operating system (e.g., Windows NT, 95/98/2000/CE/Mobile, OS2, UNIX, Linux, Solaris, MacOS, PalmOS, etc.) as well as various conventional support software and drivers typically associated with computers. A web-client may implement security protocols such as Secure Sockets Layer (SSL) and Transport Layer Security (TLS). A web-client may implement one or more application layer protocols, including, for example, http, https, ftp, and sftp. Transactions originating at a web client may pass through a firewall (not shown; see below) in order to prevent unauthorized access from users of other networks.

A network 104 may comprise any electronic communications system or method which incorporates software and/or hardware components. Communication may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant, smart phone, cellular phone (e.g., iPhone®, Palm Pilot®, Blackberry®), kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although a network 104 may be described herein as being implemented with TCP/IP communications protocols, the network 104 may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network 104 is in the nature of a public network, such as the Internet, it may be advantageous to presume the network 104 to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, DILIP NAIK, INTERNET STANDARDS AND PROTOCOLS (1998); JAVA 2 COMPLETE, various authors, (Sybex 1999); DEBORAH RAY AND ERIC RAY, MASTERING HTML 4.0 (1997); and LOSHIN, TCP/IP CLEARLY EXPLAINED (1997) and DAVID GOURLEY AND BRIAN TOTTY, HTTP, THE DEFINITIVE GUIDE (2002), the contents of which are hereby incorporated by reference.

The various system components described herein may be independently, separately or collectively coupled to the network 104 via one or more data links including, for example, a connection to an Internet Service Provider (ISP) over a local loop as is typically used in connection with standard modem communication, cable modem, Dish networks, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods, see, e.g., GILBERT HELD, UNDERSTANDING DATA COMMUNICATIONS (1996), which is hereby incorporated by reference. It is noted that the network 104 may be implemented variously. For example, network 104 may be implemented as an interactive television (ITV) network. The systems and methods disclosed herein contemplate the use, sale and/or distribution of any goods, services or information over any network having functionality similar to that described above with reference to network 104.

With reference now to FIG. 2, a process 200 for synchronizing a transaction account issuer system 106 with an accounting software system 102 is disclosed. In various embodiments, a customer may select a transaction account or a plurality of transaction accounts to synchronize with an accounting software system 102. This is illustrated, in general, at FIG. 3, where a customer may, in various embodiments, be presented with a visual presentation 302 of a variety of transaction account instruments owned by or associated with the customer, each of which may be selected by the customer as show. For instance, in this example, the customer A has selected its “plum” card (simply a type of transaction account instrument), as shown with reference to numeral 304. In addition, a customer may, as shown with reference to numeral 306, select from a drop down menu or the like an accounting software username to associate with or link to a selected transaction instrument.

Process 200 may continue, as depicted with regard to FIG. 2, with a selection by a customer of one or more categories of metadata associated with or provided by the accounting software system 102 (step 204). The customer, having selected a particular category of metadata, may further select one or more metadata labels within the selected category to import to the transaction account issuer system 106, which the issuer system 106 software may display (e.g., via an online transaction account statement) for the customer (step 206). This portion of the process 200 is generally depicted at FIG. 4, where the accounting software system 102 requests that a customer import into the transaction account issuer system 106 software one or more accounting software system 102 categories of metadata as well as one or more metadata labels (e.g., see the labels depicted generally with respect to the numeral 402) within each of the metadata categories.

Further, in various embodiments, having selected one or more categories of metadata and/or one or more metadata labels within each category, the transaction account issuer system 106 may receive each of the selected metadata categories and/or metadata labels (step 208). The transaction account issuer system 106 may further, and in various embodiments, receive one or more ROCs associated with each of the selected transaction account instruments (as described above) (step 210). ROCs may be received from one or more merchant systems coupled, via a network for example, the transaction account issuer system 106. Having received a ROC, the transaction account issuer system 106 may store the ROC and/or store the ROC as part of a statement of charges (e.g., an online statement of charges) associated with the transaction account against which the ROC is debited.

In addition, in various embodiments, the transaction account issuer system 106 may notify the customer associated with the one or more selected transaction accounts against which a ROC has been debited (in real time and/or near real time) that a ROC has been debited against such an account (step 212). The customer may be notified by way of a variety of notification channels, including by way of a text message, email, telephone call and the like delivered to the customers mobile communications device and/or to any other web-client and/or account accessible via any web-client associated with the customer. This notification in real time and or, again, near real time.

In response to receiving such a notification and/or at a customer's convenience, a customer may sign into the transaction account issuer system 106 software to review and/or manage the customer's online statement of charges or ROCs (step 214). For example, as shown with respect to FIG. 5, a customer may sign into the transaction account issuer system 106 software, which may present, as shown, a list of ROCs debited to a particular transaction account. Each ROC may appear with a variety of metadata categories, such as, for example, categories for status 502, date 504, description of the ROC 506, card member who incurred the ROC 508 (e.g., where the transaction account comprises a corporate account associated with a variety of users or employees of a customer), expense category 510, payee 512, customer job 514, class 516, amount 518, and the like. Each metadata category may be further associated with a drop down or other option for the selection of a metadata label (e.g., such as the example metadata labels shown with regard to the reference numeral 520), from which a customer may select, with respect to each metadata category, one or more associated metadata labels.

In addition, a customer may photograph or otherwise acquire a digital image (or data) of a receipt associated with a ROC, upload the image of the receipt to the transaction account issuer system 106, whereupon the image of the receipt may be associated (automatically and/or manually by the customer) with a particular ROC.

A customer, having signed into the transaction account issuer system 106, may select (e.g., from a drop down list as described above) one or more metadata category or categories and/or one or more metadata labels to associate with each listed ROC (step 216). The customer may make this selection using the transaction account issuer system software 106, the accounting software system 102, and/or any other application communicatively coupled to either system, such as a system configured to match a receipt to a transaction, such as those systems described by U.S. patent application Ser. No. 13/827,605, entitled SYSTEMS AND METHODS FOR EXPENSE MANAGEMENT, filed Mar. 14, 2014, which is hereby incorporated by reference in its entirety.

Thus, a customer may import into the customer's transaction account issuer system 106 software and from the customer's accounting software system 102, a variety of metadata categories as well as a variety of metadata labels within each category, such that the customer may easily and quickly associate one or more metadata categories and/or one or more metadata labels within each category with each ROC. In addition, having populated within the customer's transaction account issuer system 106, such data for each ROC, the customer may export or transmit the classified and labeled ROC and/or ROCs back to the transaction accounting software system 102, such that the transaction accounting software system 102 is synchronized or reconciled with the transaction account issuer system software 106 (step 218).

In the detailed description herein, references to “one embodiment”, “an embodiment”, “an example embodiment”, “various embodiments”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. After reading the description, it will be apparent to one skilled in the relevant art(s) how to implement the disclosure in certain embodiments.

In various embodiments, the methods described herein are implemented using the various particular machines described herein. The methods described herein may be implemented using the particular machines, and those hereinafter developed, in any suitable combination, as would be appreciated immediately by one skilled in the art. Further, as is unambiguous from this disclosure, the methods described herein may result in various transformations of certain articles.

For the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical system.

The various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the system. As those skilled in the art will appreciate, user computer may include an operating system (e.g., Windows NT, 95/98/2000, XP, Vista, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers. A user may include any individual, business, entity, government organization, software and/or hardware that interact with a system.

In an embodiment, various components, modules, and/or engines of system 100 may be implemented as micro-applications or micro-apps. Micro-apps are typically deployed in the context of a mobile operating system, including for example, a Palm mobile operating system, a Windows mobile operating system, an Android Operating System, Apple iOS, a Blackberry operating system and the like. The micro-app may be configured to leverage the resources of the larger operating system and associated hardware via a set of predetermined rules which govern the operations of various operating systems and hardware resources. For example, where a micro-app desires to communicate with a device or network other than the mobile device or mobile operating system, the micro-app may leverage the communication protocol of the operating system and associated device hardware under the predetermined rules of the mobile operating system. Moreover, where the micro-app desires an input from a user, the micro-app may be configured to request a response from the operating system which monitors various hardware components and then communicates a detected input from the hardware to the micro-app.

The system contemplates uses in association with web services, utility computing, pervasive and individualized computing, security and identity solutions, autonomic computing, cloud computing, commodity computing, mobility and wireless solutions, open source, biometrics, grid computing and/or mesh computing.

Any databases discussed herein may include relational, hierarchical, graphical, or object-oriented structure and/or any other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (Armonk, N.Y.), various database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Wash.), MySQL by MySQL AB (Uppsala, Sweden), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors. Various database tuning steps are contemplated to optimize database performance. For example, frequently used files such as indexes may be placed on separate file systems to reduce In/Out (“I/O”) bottlenecks.

More particularly, a “key field” partitions the database according to the high-level class of objects defined by the key field. For example, certain types of data may be designated as a key field in a plurality of related data tables and the data tables may then be linked on the basis of the type of data in the key field. The data corresponding to the key field in each of the linked data tables is preferably the same or of the same type. However, data tables having similar, though not identical, data in the key fields may also be linked by using AGREP, for example. In accordance with one embodiment, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); Binary Large Object (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.

In one exemplary embodiment, the ability to store a wide variety of information in different formats is facilitated by storing the information as a BLOB. Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction instrument or external to but affiliated with the financial transaction instrument. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with the financial transaction instrument by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first party, a second data set which may be stored may be provided by an unrelated second party, and yet a third data set which may be stored, may be provided by an third party unrelated to the first and second party. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data that also may be distinct from other subsets.

As stated above, in various embodiments, the data can be stored without regard to a common format. However, in one exemplary embodiment, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data onto the financial transaction instrument. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header”, “header”, “trailer”, or “status”, herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set; e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein.

The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified users may be permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate.

The data, including the header or trailer may be received by a stand alone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in one embodiment, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the transaction instrument user at the stand alone device, the appropriate option for the action to be taken. The system may contemplate a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the transaction instrument in relation to the appropriate data.

One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of the system may consist of any combination thereof at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.

A firewall may comprise any hardware and/or software suitably configured to protect system 100 components and/or enterprise computing resources from users of other networks. Further, a firewall may be configured to limit or restrict access to various systems and components behind the firewall for web clients connecting through a web server. A firewall may reside in varying configurations including Stateful Inspection, Proxy based, access control lists, and Packet Filtering among others. A firewall may be integrated within a web server or any other CMS components or may further reside as a separate entity. A firewall may implement network address translation (“NAT”) and/or network address port translation (“NAPT”). A firewall may accommodate various tunneling protocols to facilitate secure communications, such as those used in virtual private networking. A firewall may implement a demilitarized zone (“DMZ”) to facilitate communications with a public network such as the Internet. A firewall may be integrated as software within an Internet server, any other application server components or may reside within another computing device or may take the form of a standalone hardware component.

Encryption may be performed by way of any of the techniques now available in the art or which may become available—e.g., Twofish, RSA, El Gamal, Schorr signature, DSA, PGP, PKI, and symmetric and asymmetric cryptosystems.

The computers discussed herein may provide a suitable website or other Internet-based graphical user interface which is accessible by users. In one embodiment, the Microsoft Internet Information Server (IIS), Microsoft Transaction Server (MTS), and Microsoft SQL Server, are used in conjunction with the Microsoft operating system, Microsoft NT web server software, a Microsoft SQL Server database system, and a Microsoft Commerce Server. Additionally, components such as Access or Microsoft SQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be used to provide an Active Data Object (ADO) compliant database management system. In one embodiment, the Apache web server is used in conjunction with a Linux operating system, a MySQL database, and the Perl, PHP, and/or Python programming languages.

Any of the communications, inputs, storage, databases or displays discussed herein may be facilitated through a website having web pages. The term “web page” as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, Java applets, JavaScript, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), AJAX (Asynchronous Javascript And XML), helper applications, plug-ins, and the like. A server may include a web service that receives a request from a web server, the request including a URL (http://yahoo.com/stockquotes/ge) and an IP address (123.56.789.234). The web server retrieves the appropriate web pages and sends the data or applications for the web pages to the IP address. Web services are applications that are capable of interacting with other applications over a communications means, such as the internet. Web services are typically based on standards or protocols such as XML, SOAP, AJAX, WSDL and UDDI. Web services methods are well known in the art, and are covered in many standard texts. See, e.g., ALEX NGHIEM, IT WEB SERVICES: A ROADMAP FOR THE ENTERPRISE (2003), hereby incorporated by reference.

Middleware may include any hardware and/or software suitably configured to facilitate communications and/or process transactions between disparate computing systems. Middleware components are commercially available and known in the art. Middleware may be implemented through commercially available hardware and/or software, through custom hardware and/or software components, or through a combination thereof. Middleware may reside in a variety of configurations and may exist as a standalone system or may be a software component residing on the Internet server. Middleware may be configured to process transactions between the various components of an application server and any number of internal or external systems for any of the purposes disclosed herein. WebSphere MQ™ (formerly MQSeries) by IBM, Inc. (Armonk, N.Y.) is an example of a commercially available middleware product. An Enterprise Service Bus (“ESB”) application is another example of middleware.

Practitioners will also appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and the like.

The system and method may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the system may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the system may be implemented with any programming or scripting language such as C, C++, C#, Java, JavaScript, VBScript, Macromedia Cold Fusion, COBOL, Microsoft Active Server Pages, assembly, PERL, PHP, awk, Python, Visual Basic, SQL Stored Procedures, PL/SQL, any UNIX shell script, and extensible markup language (XML) with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the system may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. Still further, the system could be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “Java Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.

As used herein, the term “end user”, “consumer”, “customer”, “cardmember”, “business” or “merchant” may be used interchangeably with each other, and each shall mean any person, entity, machine, hardware, software or business. A bank may be part of the system, but the bank may represent other types of card issuing institutions, such as credit card companies, card sponsoring companies, or third party issuers under contract with financial institutions. It is further noted that other participants may be involved in some phases of the transaction, such as an intermediary settlement institution, but these participants are not shown.

Each participant is equipped with a computing device in order to interact with the system and facilitate online commerce transactions. The customer has a computing unit in the form of a personal computer, although other types of computing units may be used including laptops, notebooks, hand held computers, set-top boxes, cellular telephones, touch-tone telephones and the like. The merchant has a computing unit implemented in the form of a computer-server, although other implementations are contemplated by the system. The bank has a computing center shown as a main frame computer. However, the bank computing center may be implemented in other forms, such as a mini-computer, a PC server, a network of computers located in the same of different geographic locations, or the like. Moreover, the system contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein.

The merchant computer and the bank computer may be interconnected via a second network, referred to as a payment network. The payment network which may be part of certain transactions represents existing proprietary networks that presently accommodate transactions for credit cards, debit cards, and other types of financial/banking cards. The payment network is a closed network that is assumed to be secure from eavesdroppers. Exemplary transaction networks may include the American Express®, VisaNet® and the Veriphone® networks.

The electronic commerce system may be implemented at the customer and issuing bank. In an exemplary implementation, the electronic commerce system is implemented as computer software modules loaded onto the customer computer and the banking computing center. The merchant computer does not require any additional software to participate in the online commerce transactions supported by the online commerce system.

As will be appreciated by one of ordinary skill in the art, the system may be embodied as a customization of an existing system, an add-on product, upgraded software, a stand alone system, a distributed system, a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, the system may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, the system may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like.

The system and method is described herein with reference to screen shots, block diagrams and flowchart illustrations of methods, apparatus (e.g., systems), and computer program products according to various embodiments. It will be understood that each functional block of the block diagrams and the flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by computer program instructions.

These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, can be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, webpages, websites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of windows, webpages, web forms, popup windows, prompts and the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single webpages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple webpages and/or windows but have been combined for simplicity.

Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. The scope of the disclosure is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to ‘at least one of A, B, and C.’ or ‘at least one of A, B, or C’ is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. Although the inventions have been described as a method in certain embodiments, it is contemplated that it may be embodied as computer program instructions on a tangible computer-readable carrier, such as a magnetic or optical memory or a magnetic or optical disk. All structural, chemical, and functional equivalents to the elements of the above-described exemplary embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the present disclosure, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase “means for.” As used herein, the terms “comprises”, “comprising”, or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. 

What is claimed is:
 1. A method comprising: receiving, by a payment processor computer-based system, a category of metadata from an accounting software system; receiving, by the computer-based system, a plurality of metadata labels associated with the category of metadata from the accounting software; receiving, by the computer-based system, a ROC; receiving, by the computer-based system, an association of one of the plurality of the metadata labels with the ROC; and transmitting, by the computer-based system, the ROC and the association of the one of the plurality of the metadata labels with the ROC to the accounting software system.
 2. The method of claim 1, wherein one of the categories of metadata comprises a card member name.
 3. The method of claim 1, wherein one of the categories of metadata comprises an image of a receipt associated with the ROC.
 4. The method of claim 1, wherein one of the categories of metadata comprises a description.
 5. The method of claim 1, further comprising receiving, by the computer-based system, an image of a receipt associated with the ROC and associating the image with the ROC.
 6. The method of claim 1, wherein ROCs stored by the accounting software system are synchronized with ROCs stored by the computer-based system in response to the transmitting.
 7. The method of claim 1, further comprising notifying, by the computer-based system, a customer in response to receiving the ROC.
 8. The method of claim 7, wherein the notifying occurs in real time.
 9. An article of manufacture including a non-transitory, tangible computer readable storage medium having instructions stored thereon that, in response to execution by a payment processor computer-based system, cause the computer-based system to perform operations comprising: receiving, by the computer-based system, a category of metadata from the accounting software system; receiving, by the computer-based system, a plurality of metadata labels associated with the category of metadata from the accounting software system; receiving, by the computer-based system, a ROC; receiving, by the computer-based system, an association of one of the plurality of the metadata labels with the ROC; and transmitting, by the computer-based system, the ROC and the association of the one of the plurality of the metadata labels with the ROC to the accounting software system.
 10. The article of claim 9, wherein one of the categories of metadata comprises a card member name.
 11. The article of claim 9, wherein one of the categories of metadata comprises an image of a receipt associated with the ROC.
 12. The article of claim 9, wherein one of the categories of metadata comprises a description.
 13. The article of claim 9, further comprising receiving, by the computer-based system, an image of a receipt associated with the ROC and associating the image with the ROC.
 14. The article of claim 9, wherein ROCs stored by the accounting software are synchronized with ROCs stored by the computer-based system in response to the transmitting.
 15. The article of claim 9, further comprising notifying, by the computer-based system, a customer in response to receiving the ROC.
 16. The article of claim 13, wherein the notifying occurs in real time.
 17. A system comprising: a tangible, non-transitory memory communicating with a processor configured to synchronize with an accounting software system, the tangible, non-transitory memory having instructions stored thereon that, in response to execution by the processor, cause the processor to perform operations; receiving, by the processor, a category of metadata from the accounting software system; receiving, by the processor, a plurality of metadata labels associated with the category of metadata from the accounting software system; receiving, by the processor, a ROC; receiving, by the processor, an association of one of the plurality of the metadata labels with the ROC; and transmitting, by the processor, the ROC and the association of the one of the plurality of the metadata labels with the ROC to the accounting software system.
 18. The system of claim 15, wherein one of the categories of metadata comprises a card member name.
 19. The system of claim 15, wherein one of the categories of metadata comprises an image of a receipt associated with the ROC.
 20. The system of claim 15, wherein one of the categories of metadata comprises a description. 